Skip to content

Conversation

@stroebitzer
Copy link
Member

@stroebitzer stroebitzer commented Jul 24, 2025

What this PR does / why we need it:

link in readme does not work

Which issue(s) this PR fixes:
/kind documentation

Special notes for your reviewer:

Does this PR introduce a user-facing change? Then add your Release Note here:

NONE

Documentation:

NONE

@kubermatic-bot kubermatic-bot added kind/documentation Categorizes issue or PR as related to documentation. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/docs-needed Indicates that a PR should not merge because it's missing one of the documentation labels. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 24, 2025
@kron4eg
Copy link
Member

kron4eg commented Jul 24, 2025

-[addons-docs]: (https://docs.kubermatic.com/kubeone/v1.10/guides/addons/)
-[backups-addon]: (./backups-restic)
-[restic]: (https://restic.net/)
+[addons-docs]: https://docs.kubermatic.com/kubeone/v1.10/guides/addons/
+[backups-addon]: backups-restic/README.md

@kron4eg kron4eg changed the title fix small issue on addons readme docs: fix markdown link syntax in addons README Jan 21, 2026
@kubermatic-bot kubermatic-bot added docs/none Denotes a PR that doesn't need documentation (changes). release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/docs-needed Indicates that a PR should not merge because it's missing one of the documentation labels. labels Jan 21, 2026
@kron4eg kron4eg force-pushed the fix-addons-readme-issue branch from 2a0428e to 6e69a18 Compare January 21, 2026 08:20
@kubermatic-bot kubermatic-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 21, 2026
@kron4eg
Copy link
Member

kron4eg commented Jan 21, 2026

/approve
/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Jan 21, 2026
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

DetailsGit tree hash: fbbf1b8a06a75a217cc8a24b89ef1d85068aeb30

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kron4eg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 21, 2026
@kubermatic-bot kubermatic-bot merged commit 661961f into kubermatic:main Jan 21, 2026
13 checks passed
@kubermatic-bot kubermatic-bot added this to the KubeOne 1.13 milestone Jan 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants